Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1259

reference
482-tree-1
name
1259
tree-preservation-order

undefined

482-tpo-1
uprn
address-text
point
POINT (-1.023420 50.882765)
geometry
MULTIPOLYGON (((-1.023335 50.882756,-1.023338 50.882773,-1.023350 50.882788,-1.023369 50.882800,-1.023393 50.882808,-1.023419 50.882811,-1.023445 50.882809,-1.023469 50.882801,-1.023488 50.882789,-1.023501 50.882774,-1.023505 50.882758,-1.023501 50.882741,-1.023490 50.882726,-1.023471 50.882714,-1.023447 50.882706,-1.023421 50.882703,-1.023395 50.882706,-1.023371 50.882713,-1.023352 50.882725,-1.023339 50.882740,-1.023335 50.882756)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL